When I try to create rules extension it errors our saying "MV reference attributes cannot be defined as source attributes". How to solve this?

I am trying to export User data out of MV to an external sql table. One of the attributes is department.

reference in MV to string in SQL. Thanks!

You need to have an advanced flow rule and convert it in code, C# or VB. 

What is the attribute reference, Manager?

This case assumes you are trying to populate Managers DisplayName.  Assuming that the manager has an attribute employeeID and the managerID is an attribute (EmployeeID of manager) stored on users properties.

            case "Manager":

                    if (mventry["managerID"].IsPresent)

                    {

                        MVEntry[] mveManager;

                        mveManager = Utils.FindMVEntries("employeeID", mventry["managerID"].Value);

if (mveManager.Length == 1)

                        {

                            if (mveManager[0]["DisplayName"].IsPresent)

                            {

                                csentry["manager"].Value = mveManager[0]["DisplayName"].Value;

                                break;

                            }

                            else

                            {

                                break;

                            }

                        }

                        else

                        {

                            break;

                        }

                     }

                    else

                    {

                        break;

                    }

I tried to create an advanced flow - export. Sync engine is throwing the error as I mentioned above.

Screenshot attached.

.

Read my manager sample. You cannot pick a reference attribute, that is true, but there are methods (As described) to get what you want. 

Once again, what is the attribute you want to export??

I want to export Manager. In my case, Only the Manager reference attribute is attached to user. I don't have any other manager attributes(like Manager ID) attached to user.

Import the employeeid or another attribute that is unique and follow my sample

I assume in the sync engine, you have ManagerID (MV string) advanced flow export to Manager(sql string). In  my case, i dont have any other manager information stored in user record.

You have 2 options: 1. Import the managerid attribute into user managerid in mv and use my code Or 2. In FIM portal, populate managername with a displayName of manager (or another attribute you like) and then export it -Extend Portal schema. Create an attribute called managerName as string in portal and bind it to user object -Create an action wf that sets managerName attribute from [manager/displayname] -Create a set for allusers with a criteria firstname="dummy". -Create an mpr to run this wf on set allusers in transition in. -Change the criteria of set allusers, remove the firstname="dummy" -Extend MV schema. Create an attribute called managerName in mv for person object -Create an import flow on fimma to bring managerName to mv -Create an export flow for managername to manager in sql ma Let me know if you need help with any of these steps.

Thanks. I got what you are saying. I was just wondering if there is any other way to solve this without creating new attributes in portal or MV.

Yes there is. And I told you. You want a direct mapping from reference agtribute. That is not possible.

In both the options you have mentioned, I have to create new attributes. either managerid or managername and populate them with values before exporting them. In this case, there is no mapping of reference. If the new attributes I create are string, then where the reference comes into picture? I will be just passing a string to string.

1. If creating an attribute is an inconvenience to you, you can always use an existing one. I prefer to create it because I can name it to something that makes sense to me.  Both MV and Portal have a large schema and you can pick an existing attribute to use.

2. How to get the reference? I showed you a detailed step by step how to get that. This manager is a user and has some properties, right? so any of them can be read using the WF I explained to you. [/manager/DisplayName]. This takes the displayName as string, which is exactly what the reference is.

3. If you don't want to do any work and just have a plug and play device, then this is not the place to look for it.

4. I am sorry, but I have done lost of work to give you all the help you need (Free of charge, when I make a living with doing this). This is a very classical scenario and either of the options I gave you would take me less then 30 minutes to implemented. I spent more time with this thread then it would have taken me to implemented it. So did you. I honestly don't see the big deal. 

5. If you are not comfortable with making this little effort, then perhaps you should hire an expert. I am available for a very reasonable rate.

lol. you are funny. From your explanation, I sure know that I don't need you and you dont understand what I am talking about.